home *** CD-ROM | disk | FTP | other *** search
- Path: solon.com!not-for-mail
- From: seebs@solutions.solon.com (Peter Seebach)
- Newsgroups: comp.lang.misc,comp.lang.c,comp.lang.pl1,comp.lang.apl
- Subject: Re: GOTO controversy
- Date: 5 Apr 1996 23:55:12 -0600
- Organization: Usenet Fact Police (Undercover)
- Message-ID: <4k5100$3c5@solutions.solon.com>
- References: <314FB5F5.259B@simi.is> <4jq2en$g2q@news.cais.com> <AD87DB279668D9F74@mcdiala15.it.luc.edu> <4k3fvg$p1o@loki.tor.hookup.net>
- Reply-To: seebs@solon.com
- NNTP-Posting-Host: solutions.solon.com
-
- In article <4k3fvg$p1o@loki.tor.hookup.net>,
- Rajendra Singh <Rajendra_Singh@msn.com> wrote:
- >VArase@varase.it.luc.edu (Verne Arase) wrote:
-
- >>I avoid recursion in _any_ production code, no matter how I can minimize
- >>the stack frame.
-
- >I wholly agree. I do the same for my production code. It is
- >especially important when you're producing mission critical
- >applications!
-
- I dunno. I am unable to convince myself that recursion is not the best way to
- do things like a merge sort. I just make sure that I can prove it's no
- more than log(n), and that it's sane. For most of my apps, this means that
- I'd run out of memory to allocate sortable objects before the stack space
- would be an issue.
-
- -s
- --
- Peter Seebach - seebs@solon.com - Copyright 1996 Peter Seebach.
- C/Unix wizard -- C/Unix questions? Send mail for help. No, really!
- FUCK the communications decency act. Goddamned government. [literally.]
- The *other* C FAQ - http://www.solon.com/~seebs/c/c-iaq.html
-